Note: We may want to add a test to see what happens when two contracts in different modules are compiled with the same name (This was a concern that was present in the previous implementation)

There's similar changes which would have to be made to the wasm crate here in order to be consistent.

My preference on this is that we remove support for compiling contracts in TS for now as we're going to be making too many breaking changes. @kobyhallx

Ideally we have this for offsite, so they can compile and make tests in typescript. Its not a hard condition and if it makes the lives of tooling folks hard we can find an alternative.

I'm guessing the painpoint you are referring to is when we are developing on master since, once we cut a release the ts and native should be synced up?

Ideally we have this for offsite, so they can compile and make tests in typescript. Its not a hard condition and if it makes the lives of tooling folks hard we can find an alternative.

In that case we need to update noir_wasm so that it returns a similar build artifact for contracts as it will currently return incompatible values relative to the CLI.